Method, apparatus and article to remotely associate wireless communications devices with subscriber identities and/or proxy wireless communications devices

ABSTRACT

Apparatus and methods provide remote access to subscriber identity information and subscriber configuration information stored on one or more subscriber identity modules (SIMs), to allow remote configuration of wireless communications devices. A SIM server provides access to the SIMs, a SIM librarian catalogs the SIMs, and a SIM accounting system tracks and/bills for SIM usage. Apparatus and methods provide remote access to proxy wireless communications devices, allowing such devices to operate as if actually present in the remote locations.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention generally relates to wireless communications, forexample, cellular communications.

2. Description of the Related Art

The use of wireless communications is rapidly growing. Wirelesscommunications devices such as cellular phones and wireless personaldigital assistants (“PDA”) are ubiquitous in today's culture. Thesedevices transmit and/or receive audio and/or data wirelessly. Forexample, cellular phones may transmit and receive audio, text messaging,and may even allow access to the Internet. PDAs typically transmitand/or receive electronic mail (“e-mail”) and may provide access to theWorldwide Web (“WWW”). These wireless communications devices aretypically handheld battery powered devices which a user operates usingkeyed entries, stylus strokes, and/or voice activation by way of a userinterface (“UI”). Many wireless communications devices also include adisplay for displaying information and/or a command menu which formspart of the UI. Wireless communications devices also typically includean antenna, a transceiver or a transmitter and receiver, and a processorsuch as a microprocessor, application specific integrated circuit(“ASIC”) and/or digital signal processor (“DSP”) for controllingoperation.

The wireless communications devices rely on wireless communicationsservice providers for providing subscribed services. The wirelesscommunications service providers operate wireless communications serviceprovider systems that provide for registration, authentication, locationupdating, handovers, and call routing. The wireless communicationsservice provider systems typically employ a Home Location Register(“HLR”) and a Visitor Location Register (“VLR”) to provide call routingand roaming. The HLR contains all of the administrative information foreach subscriber registered with the wireless communications serviceprovider, along with current location information for a wirelesscommunications device currently associated with the subscriber. The VLRcontains selected administrative information from the HLR which isrequired for call control and for providing subscribed services for eachwireless communications device currently within a geographical areaservice by the VLR.

Many wireless communications devices include computer-readable mediacommonly referred to as a subscriber identity module (“SIM”) thatcontains subscriber related data or information. While the SIM typicallytakes the form of a physically removable device such as a “smartcard” orsimilar article, in certain embodiments the SIM may be permanently fixedin the wireless communications device. The SIM typically includes amicrochip having a microprocessor and persistent memory such as erasableprogrammable read-only memory (“EPROM”). In addition to otherinformation, the SIM may store one or more identifiers that uniquelyidentify a subscriber. Thus, a wireless communications device may beassociated or configured with a subscriber's specific identity andrelated information by physically placing the appropriate SIM into a SIMslot of the wireless communication device.

While other wireless protocols exist (i.e., TDMA, CDMA), one of the mostpopular of the numerous wireless protocols is the European Global Systemfor Mobile Communications (“GSM”) standard. Under GSM, the SIM stores anidentifier commonly known as an International Mobile Subscriber Identity(“IMSI”). The IMSI is hardcoded in the SIM and is protected againstchange or tampering. The HLR logically relates the IMSI to the telephonenumber (i.e., Mobile Subscriber ISDN) associated with the subscriber, aswell as relating the IMSI to the services subscribed to by thesubscriber. Also under GSM, the SIM stores a second identifier in theform of a secret key for subscriber authentication and/or communicationsencryption, as discussed below. The SIM may be protected againstunauthorized use by way of a password and/or personal identity number.

Under GSM, a separate identifier, commonly known as an InternationalMobile Equipment Identity (“IMEI”), is hardwired or hardcoded into thewireless communications device, and is used to uniquely identify thewireless communications device. The IMSI and IMEI are independent,providing personal mobility by allowing a subscriber to use a SIM in avariety of different wireless communications devices at different times.

In use, the wireless communications service provider authenticates thesubscriber at a start of each call, and also authenticates thesubscriber at intervals during the call. The wireless communicationsservice provider system typically relies on the Signaling System Number7 (“SS7”) for signaling between the various functional entities, such aschallenging the wireless communications device with a request forauthorization. As discussed above, each subscriber is assigned an IMSIand a secret key. One copy of the secret key resides on the SIM andanother copy of the secret key resides with the wireless communicationsservice provider in an Authentication Center (“AuC”). Duringauthentication, the AuC challenges the wireless communications device bygenerating and transmitting a random number to the wirelesscommunications device as part of an authentication request. The AuC andthe wireless communications device each generate a respective response,commonly referred to as a “signed response” (“SRES”) based on the secretkey and random number using a ciphering algorithm, commonly referred toas “A3”. The wireless communications device transmits the SRES back tothe AuC, which authenticates the subscriber if the SRES generated by thewireless communications device matches the SRES generated by the AuC.The wireless communications device and AuC may also generate a cipheringkey for encrypting communications based on the random number and secretkey using a second ciphering algorithm, commonly referred to as “A8”.

The wireless communications service provider also verifies a status ofthe wireless communications device, for example, at a start of eachcall. The wireless communications service provider maintains anEquipment Identity Register (EIR) which stores a list of all IMEIs onthe service provider's network and a status for each correspondingwireless communications device. Typically, the EIR will employ threelevels of status, a “white-list” status indicating that the wirelesscommunications device is approved to be connected, a “gray-list” statusindicating that the wireless communications device may be connected butthat problems may exist, and a “black-list” status indicating that thewireless communications device may not be connected due to a problem,for example, where the device has been reported stolen or is not of anapproved type for use with the wireless communications service providersystem.

The SIM may also store additional subscriber related information such assubscriber configuration or customization information, for customconfiguring the wireless communications device to the subscriber'sspecific requirements or preferences. For example, the subscriberconfiguration information may identify a home service area, a list offrequently called numbers, voice recognition samples, a list of mostrecent calls received and/or placed by the subscriber, a notificationsetting (e.g., ring or vibrate), a list of short messages, etc.

Thus, wireless communication devices typically utilizes subscriberidentification information such as an IMSI and/or secret key, as well assubscriber configuration information. The subscriber identificationinformation is hardwired into a chip or card in order to preventtampering, while the subscriber configuration information is typicallysoft coded to allow updating. While the SIM may be replaceable in somewireless communications devices, replacement typically requires thewireless communications device and the replacement SIM to be in the samephysical location.

Wireless communications systems and devices may require testing toassure performance. One method of testing is to physically transitportions of the area covered by the wireless communications system whileoperating a wireless communications device. Another approach suggestedin U.S. Pat. Nos. 5,875,398 and 6,230,006 and employs remotely operatedtest platforms which are pre-positioned at a variety of locations in thewireless communications coverage area. The remote test platformstypically include two or more wireless communications devices which maybe controlled by a local or central controller to place and receivecalls in selected coverage areas.

BRIEF SUMMARY OF THE INVENTION

Remote testing may be limited by the subscriber identificationinformation and/or subscriber configuration information stored in thewireless communications devices at the remote test platforms. Updatingthis information would typically require a visit by a technician. Therequirement that a SIM be physically received in a SIM slot of awireless communications device also requires the ownership of more SIMsthan would be typically be desired during actual testing.

In one aspect, a system to dynamically associate wireless communicationsdevices with subscriber identities includes a subscriber identity modulebank having a number of positions for respectively receiving subscriberidentity modules and a subscriber identity module server having acommunications port to receive requests and configured to dynamicallyprovide subscriber identity information from subscriber identity modulesreceived in the respective positions, if any, to a remote wirelesscommunications client located remotely from the subscriber identitymodule bank in response to the received requests.

In another aspect, a subscriber identity module server to remotelyassociate a client wireless communications device with subscriberidentity information includes a processor, a communications port toreceive requests for subscriber identity modules, the communicationsport coupled to the processor, and at least one computer-readable mediastoring instructions that cause the processor to cause subscriberidentity information from the requested subscriber identity module to beprovided to the client wireless communications device in response to therequest, where the client wireless communications device is remote fromthe subscriber identity module server.

In another aspect, a subscriber identity module server to remotelyassociate a remote client wireless communications device with subscriberidentity information includes a processor, a communications port toreceive requests for a subscriber identity module, the communicationsport coupled to the processor, and at least one computer-readable mediastoring instructions that cause the processor to determine whether thesubscriber identity module server has access to the requested subscriberidentity module and to cause a set of subscriber identity informationfrom the requested subscriber identity module to be provided to theclient wireless communications device if has subscriber identity moduleserver has access to the requested subscriber identity module.

In another aspect, a subscriber identity module librarian to tracksubscriber identity modules for use in remotely associating wirelesscommunications devices with subscriber identity information includes aprocessor, a communications port to receive requests for subscriberidentity module address information, the communications port coupled tothe processor, and at least one computer-readable media storing a set ofaddress information for each of a number of subscriber identity modulesin a respective position of each at least one subscriber identity modulebanks remotely located from the subscriber identity module librarian,the computer-readable media storing computer-readable instructions thatcause the processor to provide subscriber identity module addressinformation in response to a request received at the communicationsport.

In yet another aspect, accounting system to track usage of a pluralityof subscriber identity modules includes a processor, at least onecommunications port coupled to each of a number of subscriber identitymodule servers to receive subscriber module request information, and atleast one computer-readable media having instructions that cause theprocessor to track usage of the subscriber identity modules by:monitoring usage of the subscriber identity modules by at least one of anumber of tracking entities.

In yet another aspect, a system to remotely operate wirelesstelecommunications devices includes a first subscriber identity modulebank having a number of positions for receiving a number of subscriberidentity modules and a first subscriber identity module serverassociated with the first subscriber identity module bank and responsiveto requests to provide subscriber identity information from thesubscriber identity modules, if any, received at the positions of theassociated subscriber identity module bank.

In yet another aspect, system to remotely operate wirelesstelecommunications devices includes a first subscriber identity modulebank having a number of positions for receiving a number of subscriberidentity modules, a first subscriber identity module server associatedwith the first subscriber identity module bank and responsive torequests to provide subscriber identity information from the subscriberidentity modules, if any, received at the positions of the associatedsubscriber identity module bank, and a subscriber identity modulelibrarian having a data structure that defines a set of relationshipsbetween a number of subscriber identity modules identifierscorresponding to respective subscriber identity modules, if any, and anetwork location of the respective subscriber identity module in anetwork.

In even another aspect, a system to remotely operate wirelesstelecommunications devices includes a first subscriber identity modulebank having a number of positions for receiving a number of subscriberidentity modules, a first subscriber identity module server associatedwith the first subscriber identity module bank and responsive torequests to provide subscriber identity information from the subscriberidentity modules, if any, received at the positions of the associatedsubscriber identity module bank, and a controller having a processorprogrammed to remotely control operation of a number of remote wirelesscommunications clients at respective remote locations with respect tothe controller, by transmitting commands over a communications channelto the remote wireless communications clients where at least one of thecommands includes a subscriber identity module identifier.

In even another aspect, a system to remotely operate wirelesstelecommunications devices includes a first subscriber identity modulebank having a number of positions for receiving a number of subscriberidentity modules, a first subscriber identity module server associatedwith the first subscriber identity module bank and responsive torequests to provide subscriber identity information from the subscriberidentity modules, if any, received at the positions of the associatedfirst subscriber identity module bank, a second subscriber identitymodule bank having a number of positions for receiving a number ofsubscriber identity modules, and a second subscriber identity moduleserver associated with the second subscriber identity module bank andresponsive to requests to provide subscriber identity information fromthe subscriber identity modules, if any, received at the positions ofthe associated second subscriber identity module bank, wherein each ofthe first and the second subscriber identity servers include arespective computer-readable media storing computer accessible addressinformation for subscriber identity modules received in each of thefirst and the second subscriber identity module banks.

In yet even another aspect, a method of remotely associating a wirelesscommunications device with subscriber identities includes receiving afirst request, determining a first subscriber identity module capable ofproviding a first set of subscriber identity information correspondingto the first request, and automatically providing the first set ofsubscriber identity information from the first subscriber identitymodule to the wireless communications device over a communications pathwhere the wireless communications device is remote from the firstsubscriber identity module.

In a further aspect, a method to remotely associate a remote clientwireless communications device with subscriber identity informationincludes receiving a request for a subscriber identity module at a firstsubscriber identity module server, determining whether the firstsubscriber identity module server has access to the requested subscriberidentity module, and causing a set of subscriber identity informationfrom the requested subscriber identity module to be provided to theclient wireless communications device if the subscriber identity moduleserver has access to the requested subscriber identity module.

In a further aspect, a method of remotely associating wirelesscommunications client with subscriber identities includes receiving afirst request from a wireless communications client, determining whetherthe received first request includes a sufficient indication ofauthorization, and automatically providing a first set of subscriberidentity information from a first subscriber identity modulecorresponding to the first request to the requesting wirelesscommunications client over a communications path if the received firstrequest includes a sufficient indication of authorization where thewireless communications device is remote from the first subscriberidentity module, and denying access to the first set of subscriberidentity information from the first subscriber identity module to therequesting wireless communications client if the received first requestdoes not include a sufficient indication of authorization.

In a further aspect, a method to remotely associate a remote wirelesscommunications client with subscriber identity information includesreceiving a set of subscriber identity information from the remotelylocated subscriber identity module in response to a requests for asubscriber identity module and operating the wireless communicationsdevice using the received subscriber identity information.

In yet a further aspect, a method of tracking subscriber identitymodules for use in remotely associating wireless communications deviceswith subscriber identities includes storing a respective set of addressinformation for each of a number of subscriber identity modules,receiving a request for subscriber identity module address information,and providing the set of subscriber identity module address informationin response to the received request.

In yet a further aspect, a method of tracking subscriber identitymodules for use in remotely associating wireless communications deviceswith subscriber identities includes receiving a subscriber identitymodule request, determining if the requested subscriber identity moduleis available in at least one of a number of associated subscriberidentity module banks, and requesting address information for therequested subscriber identity module from a remote subscriber identitymodule librarian if the requested subscriber identity module is notavailable in at least one of the number of associated subscriberidentity module banks.

In still a further aspect, a method of accounting in a wirelesscommunications system includes receiving subscriber identity moduleusage information from each of a number of subscriber identity moduleservers and for each of a number of tracking entities, monitoring theusage of each of a number of subscriber identity modules based on thereceived subscriber identity module usage information.

In still a further aspect, a method to remotely operate wirelesstelecommunications devices includes receiving a request for at least oneof a number of subscriber identity modules and responding to the requestby providing subscriber identity information from the requested one ofthe subscriber identity modules to an at least first wirelesstelecommunications device of a first remote wireless communicationsclient.

In yet still a further aspect, a method to remotely operate wirelesstelecommunications devices includes transmitting commands over acommunications channel to a remote wireless communications client havingat least one wireless communications device where at least one of thecommands includes a subscriber identity module identifier correspondingto a subscriber identity module providing subscriber identityinformation for use in operating the wireless communications device andreceiving results from the remote wireless communications client inresponse to execution of the commands.

In an additional aspect, a method of allocating access to subscriberidentity information includes providing remote access by a trackingentity to a plurality of subscriber identity modules over acommunications channel, each of the subscriber identity modules capableof providing a respective set of subscriber identity information andautomatically tracking usage of the subscriber identity modules by thetracking entity.

In yet an additional aspect, a method of operating a subscriber identitymodule server includes receiving a request at a first subscriberidentity module server for a first subscriber identity module, providingsubscriber identity information from the first subscriber identitymodule to a remote client communications device if the requested firstsubscriber identity module is accessible by the first subscriberidentity module server and providing a computer routable address to theremote client communications device if the requested first subscriberidentity module not accessible by the first subscriber identity moduleserver and is accessible by a second subscriber identity module serverfor which the first subscriber identity module server stores addressinformation.

In yet a further additional aspect, a method of remotely associating awireless communications device with subscriber identities includesreceiving a first request for a subscriber identity, determining a firstsubscriber identity module corresponding to the subscriber identity ofthe first request, and exclusively allocating the determined firstsubscriber identity module to a wireless communications device.

In even a further aspect, a remote access system to remotely accesswireless communications devices includes a wireless communicationsdevice rack having a number of positions for respectively receivingproxy wireless communications devices, and a wireless device serverhaving a communications port to receive a request for remote access to aproxy wireless communications device and configured to provide acommunications link with at least one of the proxy wirelesscommunications devices received in the respective positions of thewireless communications rack, if any, to a controlling wirelesscommunications device located remotely from the wireless communicationsrack in response to the received request for remote access to a proxywireless communications device.

In still even a further aspect, a method of providing remote access toproxy wireless communications devices by controlling wirelesscommunications devices includes receiving a first request for remoteaccess to a proxy wireless communications device, determining a firstproxy wireless communications device corresponding to the first requestfor remote access to the proxy wireless communications device, andautomatically linking the first proxy wireless communications device toa first controlling wireless communications device over a communicationspath where the first controlling wireless communications device isremote from the first proxy wireless communications device in responseto the first request for remote access to a proxy wirelesscommunications device.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

In the drawings, identical reference numbers identify similar elementsor acts. The sizes and relative positions of elements in the drawingsare not necessarily drawn to scale. For example, the shapes of variouselements and angles are not drawn to scale, and some of these elementsare arbitrarily enlarged and positioned to improve drawing legibility.Further, the particular shapes of the elements, as drawn, are notintended to convey any information regarding the actual shape of theparticular elements, and have been solely selected for ease ofrecognition in the drawings.

FIG. 1 is a diagramatic view of an exemplary SIM remote access systemincluding a number of SIM servers, associated SIM banks, remote wirelesscommunications clients, a SIM librarian computing system and a SIMaccounting computing system operating in a wireless communicationsnetwork environment according to one illustrated embodiment of theinvention.

FIG. 2 is a schematic diagram of a computing system which may beconfigured as a local or central controller computing system, a SIMserver, a SIM librarian computing system or SIM accounting computingsystem of the SIM remote access system of FIG. 1.

FIG. 3 is a schematic diagram of a SIM bank.

FIG. 4 is a schematic diagram of a remote wireless communications clientin the form of a remote test platform having a pair of wirelesscommunications devices.

FIG. 5 a logical diagram of the SIM server and SIM bank of FIG. 1.

FIG. 6 is a logical diagram of the remote communications client of FIG.1, the remote communications client taking the form of a remote testplatform having two remote wireless communications devices.

FIG. 7 is a logical diagram of the SIM librarian computing system of thewireless communications system of FIG. 1.

FIG. 8 is a flow diagram of an illustrated method of operating of theremote wireless communications client FIG. 1.

FIGS. 9A and 9B are a flow diagram of an illustrated method of operatingthe SIM server of FIG. 1.

FIG. 9C is a flow diagram of an illustrated method of exclusivelyassociating a requested SIM with a remote wireless communications clientin accordance with the method of operating the SIM server illustrated inFIGS. 9A and 9B.

FIG. 9D is a flow diagram of an illustrated method of passing achallenge and response between wireless communications client and a SIMin accordance with the method of exclusively associating a requested SIMwith a remote wireless communications client illustrated in FIG. 9C.

FIG. 10 is a flow diagram of an illustrated method of operating the SIMlibrarian of FIG. 1 to provide SIM location information.

FIG. 11 is a flow diagram of an illustrated method of operating of theSIM librarian computing system of FIG. 1 to maintain SIMlocation/identification information.

FIG. 12 is a schematic diagram of a data structure for storing SIMlocation/identification information including an number of records eachhaving a number of fields.

FIGS. 13A and 13B are a flow diagram of an illustrated method ofoperating the SIM accounting computing system of FIG. 1.

FIG. 14 is a flow diagram of an alternative illustrated method ofoperating the SIM accounting computing system of FIG. 1.

FIG. 15 is a schematic diagram of a remote wireless device access systemin use with the remote SIM access system of FIG. 1, the remote wirelessdevice access system having a rack including a number of proxy wirelesscommunications devices.

FIG. 16 is a schematic diagram of the rack of wireless communicationsdevices for use in the remote wireless communications device accesssystem of FIG. 15.

FIG. 17 is a flow diagram of a method of operating the alternativeembodiment of FIG. 15.

FIG. 18 is a flow diagram of a method of operating the SIM serveremploying caching of response to requests.

FIG. 19 is a schematic diagram of a remote access system to provideremote access to communications devices.

DETAILED DESCRIPTION OF THE INVENTION

In the following description, certain specific details are set forth inorder to provide a thorough understanding of various embodiments of theinvention. However, one skilled in the art will understand that theinvention may be practiced without these details. In other instances,well-known structures associated with computers, servers, networks,wireless communications devices and systems have not been shown ordescribed in detail to avoid unnecessarily obscuring descriptions of theembodiments of the invention.

Unless the context requires otherwise, throughout this specification andclaims which follow, the word “comprise” and variations thereof, suchas, “comprises” and “comprising” are to be construed in an open,inclusive sense, that is as “including, but not limited to.”

The headings provided herein are for convenience only and do notinterpret the scope or meaning of the claimed invention.

Wireless Communications Environment Overview

FIG. 1 shows a communications system 10 including a wirelesscommunications environment such as a cellular network 12.

The cellular network 12 includes a number of cell sites or basestations, collectively referenced as 14 and individually referenced as14 a–14 d. The cell site or base station 14 typically consists of anantenna tower, transceiver radios (i.e., base transceiver station), andradio controllers (i.e., base station controller). The base stations 14each include a transceiver or transmitter and receiver through whichradio links are established between the cellular network 12 and a numberof wireless communication clients, collectively referenced as 16 andindividually referenced as 16 a–16 d. The area served by each basestation 14 a–14 d is commonly referred to as a cell, collectivelyreferenced as 18 and individually referenced as 18 a–18 d, respectively.The cells 18 can vary in size depending upon terrain, capacity, demands,and other factors. The radio frequency that is assigned to one cell 18can be limited to the boundary of that cell 18 by controlling thetransmission power.

The cellular network 12 also includes a number of mobile telephoneswitching centers (“MSC”), collectively referenced as 20 andindividually referenced as 20 a, 20 b, located at one or more mobiletelephone switching offices (“MTSO”) which route the transmissions.Additionally, the cellular network 12 may include one or more basecellular centers (“BSC”), not shown, coupled between the base stations14 and the MSCs 20, for example, to handle call hand off. Forconvenience, the description will refer only to MSC, although oneskilled in the art will recognize that many of the functions describedas being performed by the MSC may alternatively or additionally beperformed by the BSC.

The MSC 20 constantly monitors signal strength of both the caller andreceiver, locating the next cell site when signal strength fades, andautomatically rerouting the communications to maintain thecommunications link. For example, when a wireless communications client16 moves from one cell to another cell (e.g., 18 a to 18 b), a computerat the MSC 20 a monitors the movement, and transfers (i.e., handoff) thephone call from the first base station (e.g., 14 a) to the new basestation (e.g., 14 b) at the appropriate time. The transfer willtypically include switching of radio frequency. The transfer should betransparent to the users. Thus, the MSC 20 acts like a standard PSTN orISDN switching node, and additionally provides mobile subscriber relatedfunctions such as registration, authentication, location updating,handovers and call routing to roaming subscribers.

As discussed in the background section, the MSC 20 typically employs twodatabases (e.g., HLR and VLR) for tracking subscribers and routingcalls. The MSC 20 typically employs a database (e.g., AuC) forauthenticating subscribers, and a separate database (e.g., EIR) forverifying the equipment. The MSC 20 typically allocates a routing numberto each of the calls that the MSC 20 is switching. While the routingnumber is different than the unique subscriber identifier (e.g., IMSI)and the unique equipment identifier (e.g., IMEI), MTSO may define arelationship between the routing number and the subscriber and/orequipment identifiers associated with each wireless communicationsclient 16. These identifiers allows the MSC 20 to track and coordinateall wireless communications clients 16 in its service area, and alsoallows the MSC 20 to determine the validity of the call and caller.

The MSC 20 routes calls using the communications network 22, which mayinclude wireless as well as landline communications links. While thecellular network 12 provides wireless communications service andlandline networks typically provide conventional communications service,such as conventional telephone service, these networks and servicesgenerally overlap. For example, a wireless communications user can placea call through the cellular network to the landline network to establisha communications link with a conventional communications device, such asa telephone. Conversely, a conventional communications device user canplace a call through a landline network to a cellular network toestablish a communications link with a wireless communications devicesuch as a cellular phone. Thus, the cellular network 12 including thecommunications network 22 often includes communications links that maybe considered part of the landline network, including POTS lines, trunklines, and optical fiber to name a few.

SIM Remote Access System

The communications system 10 also includes a SIM remote access system 24to provide remote access to information stored on SIMs. The SIM remoteaccess system 24 includes a number of SIM servers, collectivelyreferenced as 26 and individually referenced as 26 a–26 e, and a numberof SIM banks, collectively referenced as 28 and individually referencedas 28 a–28 g, for receiving one or more SIMs. As used throughout thisspecification and claims, the term SIM refers to any computer- orprocessor-readable media that stores unique subscriber identifyinginformation, such as, but not limited to, an IMSI and/or secret key,and/or that stores subscriber customization or configurationinformation.

As illustrated, a SIM server 26 b may be associated with one SIM bank 28b, or a SIM server 26 a may be associated with more than one SIM bank 28a, 28 f, 28 g. The SIM banks 28 may be housed separately from theassociated SIM server 26 a, for example, SIM banks 28 a, 28 f, 28 g andSIM server 26 a. Alternatively, the SIM banks 28 may be commonly housedwith the associated servers 26, for example, SIM banks 28 b–28 d and SIMservers 26 b–26 d, respectively, as illustrated by the broken linetherebetween.

Also as illustrated in FIG. 1, the SIM servers 26 and SIM banks 28 maybe logically arranged in groups, identified by broken line boxes 30 a–30c. Each SIM server 26 stores information regarding the SIMs associatedwith that SIM server 26. In the illustrated embodiment, each SIM server26 in a group 30 also stores information about the SIMs associated withthe other SIM servers 26 in the group 30. Thus, the SIM server 26 b notonly stores information regarding the SIMs in SIM bank 28 b, but alsostores information regarding the SIMs in the SIM banks 28 c, 28 d of thesame group 30 b. The stored information may provide an easy oralternative method of identifying the particular SIM or characteristicsof the SIM, as explained in detail below.

The wireless communications clients 16 may access the information storedor provided by the SIMs through the communications network 22 via therespective associated SIM servers 26. The remote SIM access system 24may be composed of any one or more of the SIM servers 26 and SIM bank 28in any one or more of the relationships illustrated in FIG. 1 or inother relationships not specifically illustrated.

The remote SIM access system 24 may include one or more controllers,collectively referenced as 32 and individually referenced as 32 a, 32 b,to remotely control one or more wireless communications clients 16. Thecontrollers 32 can send commands to the wireless communications clients16 via the communications network 22, allowing automatic or manualremote operation of the wireless communications client 16 from one ormore local or central locations. The controllers 32 may allow real timetesting by an operator of remote switches and/or wirelesscommunications. Additionally, or alternatively, the controllers 32 mayallow automated scheduled testing of remote switches and/or wirelesscommunications. Automated testing may be scheduled, for example, fornon-peak times to limit the loss of valuable cellular capacity, or maybe scheduled during peak times, for example when testing systemperformance under peak demand conditions.

The SIM remote access system 24 may also include a SIM librarian, forexample, in the form a SIM librarian computing system 34 to track thelocation of the SIMs in the various SIM banks 28 across a portion or allof the SIM remote access system 24. The SIM librarian system 34 maycommunicate with the SIM servers 26 via the communications network 22,to provide computer-routable address information for various requestedSIMs. The SIM librarian system 34 may also perform queries and/orreceive new and/or updated SIM location information via thecommunications network 22. The SIM librarian computing system 34 may mapa number of human-recognizable identifiers for each of the SIMs torespective computer-routable address information for accessing thesubscriber identity information and/or subscriber configurationinformation stored in the respective SIM. Additionally, or alternativelythe SIM librarian computing system 34 may map SIM characteristics foreach of the SIMs to respective computer-routable address information foraccessing the subscriber identity information and/or subscriberconfiguration information stored or provided by the respective SIM. Suchmappings allow the formulation of simple human-recognizable textsearches or queries to locate corresponding SIMs.

While illustrated as having one SIM librarian computing system 34, someembodiments of the SIM remote access system 24 may include more than oneSIM librarian computing system 34. Having multiple SIM librariancomputing systems 34 may provide a number of benefits, such asredundancy and faster access time, however multiple SIM librariancomputing systems 34 may produce a number of detriments, such as addedoverhead in time and cost of maintaining redundant information, and thepossibility of inconsistencies between the SIM librarian computingsystems 34.

The SIM remote access system 24 may also include an accounting systemsuch as a SIM accounting computing system 36 to account for SIM usage byone or more billing or tracking entities. The SIM accounting computingsystem 36 may receive SIM usage information from the SIM servers 26and/or the wireless communications clients 16 via the communicationsnetwork 22, as is explained in detail below.

The tracking entities may be separate companies or businesses, and/ormay be separate divisions within a single company or business. The SIMaccounting system computing 36 may allow companies to simply track SIMusage, allocate cost for SIM usage in budgeting, and/or even bill orinvoice for actual SIM usage. For example, a division within a companymay own a set of SIMs which the division routinely accesses, but thedivision may require occasional use of the SIMs of another division,which can be accounted for using the SIM accounting computing system 36.Additionally, or alternatively, an access providing business entity canown a number of SIMs, and can employ the SIM accounting computing system36 to rent or lease SIM usage to other entities. For example, under onebusiness model the access providing business entity owns a number ofSIMs and provides a number of different wireless communicationsproviders or testing companies with remote access to the SIMs using theSIM accounting computing system 36. In a variation on the businessmodel, the access providing business may also own a number of wirelesscommunications clients located in the field for remote testing. Underthis model, the access providing business may simply provide wirelesscommunications providers with access to the wireless communicationsclients, or may actually perform testing for the wireless communicationsproviders.

FIG. 1 illustrates a small number of the possible communications linkswhich may be established. For example, the controller 32 a may cause thewireless communications client 16 b in one cell 18 b to establish acommunications link, illustrated by double headed arrow 37, with awireless communications client 16 a in another cell 18 a. In anotherexample, the controller 32 a may cause the wireless communicationsclient 16 c in one cell 18 b to establish a wireless communicationslink, illustrated by double headed arrows 35, with itself, where thewireless communications client 16 c includes two separately addressablewireless communications devices 100 a, 100 b (FIG. 4). In a furtherexample, the controller 32 b may cause the wireless communicationsclient 16 d in one cell 18 d to establish a wireless communicationslink, illustrated by double headed arrow 33, with a wirelesscommunications client 16 e in the same cell 18 d. In yet a furtherexample, the controller 32 a may cause the wireless communicationsclient 16 c in one cell 18 c associated with the one MSC 20 a toestablish a wireless communications link, illustrated by double headedarrow 41, with a wireless communications client 16 d in another cell 18d through another MSC 20 b. Other variations are of course possible, aswill be recognized by one skilled in the art with an understanding ofthese teachings.

Typically, such communications links may be used to test switching inthe cellular network 12. However, such communications links may also beused to remotely provide identities and/or configurations to thewireless communications clients 16. For example, a wireless PDA 16A in aremote geographic location 18 a may take on a desired set of propertiesassociated with a SIM in a locally located SIM bank 28 a. Thus, forexample, a successive number of SIMs can be selected such that thewireless communications device 16 a is always in a “home calling area”as it travels from cell 18 a to cell 18 d. Additionally, oralternatively, the wireless client 16 can take on the identity of anydesired wireless communications device, such as a wireless PDA byremotely assigning the appropriate SIM to the wireless communicationsdevice 16.

System Hardware

FIG. 2 and the following discussion provide a brief and generaldescription of a suitable computing environment in which embodiments ofthe invention can be implemented, particularly those of FIG. 1. Althoughnot required, embodiments of the invention will be described in thegeneral context of computer-executable instructions, such as programapplication modules, objects or macros being executed by a computer.Those skilled in the relevant art will appreciate that the invention canbe practiced with other computing system configurations, includinghand-held devices, multiprocessor systems, microprocessor-based orprogrammable consumer electronics, personal computers (“PCs”), networkPCs, mini-computers, mainframe computers, and the like. The inventioncan be practiced in distributed computing environments where tasks ormodules are performed by remote processing devices, which are linkedthrough a communications network. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices.

The subject matter of FIG. 2 and the following discussion may begenerally or specifically relevant to computing systems suitable for useas any one or more of the SIM servers 26, controllers 32, SIM librariancomputing system 34, and/or SIM accounting computing system 36, ect. Inthe interest of brevity, only significant differences in hardware andoperation of the various computing systems 26, 32, 34, 36 will be setout and discussed separately.

Referring to FIG. 2, a computing system 39 includes a processing unit40, a system memory 42, and a system bus 43 that couples various systemcomponents including the system memory 42 to the processing unit 40. Thecomputing system 39 will at times be referred to in the singular herein,but this is not intended to limit the application of the invention to asingle computing system 39 since in typical embodiments, there will bemore than one computing system 39 or other device involved. The SIMremote access system 24 may employ other computing systems, such asconvention and personal computers, where the size or scale of the systemallows. The processing unit 40 may be any logic processing unit, such asone or more central processing units (“CPUs”), digital signal processors(“DSPs”), application-specific integrated circuits (“ASICs”), etc.Unless described otherwise, the construction and operation of thevarious blocks shown in FIG. 2 are of conventional design. As a result,such blocks need not be described in further detail herein, as they willbe understood by those skilled in the relevant art.

The system bus 43 can employ any known bus structures or architectures,including a memory bus with memory controller, a peripheral bus, and alocal bus. The system memory 42 includes read-only memory (“ROM”) 44 andrandom access memory (“RAM”) 46. A basic input/output system (“BIOS”)48, which can form part of the ROM 44, contains basic routines that helptransfer information between elements within the computing system 39,such as during startup.

The computing system 39 also includes a hard disk drive 50 for readingfrom and writing to a hard disk 52, and an optical disk drive 54 and amagnetic disk drive 56 for reading from and writing to removable opticaldisks 58 and magnetic disks 60, respectively. The optical disk 58 can beread by a CD-ROM, while the magnetic disk 60 can be a magnetic floppydisk or diskette. The hard disk drive 50, optical disk drive 54 andmagnetic disk drive 56 communicate with the processing unit 40 via thebus 43. The hard disk drive 50, optical disk drive 54 and magnetic diskdrive 56 may include interfaces or controllers (not shown) coupledbetween such drives and the bus 43, as is known by those skilled in therelevant art. The drives 50, 54 and 56, and their associatedcomputer-readable media, provide non-volatile storage of computerreadable instructions, data structures, program modules and other datafor the computing system 39. Although the depicted computing system 39employs hard disk 52, optical disk 58 and magnetic disk 60, thoseskilled in the relevant art will appreciate that other types ofcomputer-readable media that can store data accessible by a computer maybe employed, such a magnetic cassettes, flash memory cards, digitalvideo disks (“DVD”), Bernoulli cartridges, RAMs, ROMs, smart cards, etc.

Program modules can be stored in the system memory 42, such as anoperating system 62, one or more application programs 64, other programsor modules 66 and program data 68. The system memory 42 may also includea web client or browser 70 for permitting the computing system 39 toaccess and exchange data with sources such as website of the Internet,corporate Intranets, or other networks as described below, as well asother server applications on server computers such as those furtherdiscussed below. The browser 70 in the depicted embodiment is markuplanguage based, such as hypertext markup language (“HTML”), extensiblemarkup language (“XML”) or wireless markup language (“WML”), andoperates with markup language that use syntactically delimitedcharacters added to the data of a document to represent the structure ofthe document. A number of web clients or browsers are commercialavailable such as Netscape Navigator from America Online and InternetExplorer available from Microsoft, Redmond, Wash.

While shown in FIG. 2 as being stored in the system memory 42, theoperating system 62, application program 64, and other programs/modules66, program data 68 and browser 70 can be stored on the hard disk 52 ofthe hard disk drive 50, the optical disk 58 of the optical disk drive 54and/or the magnetic disk 60 of the magnetic disk drive 56.

The computing system 39 can operate in a networked environment usinglogical connections to one or more remote computers, such as thewireless communications clients 16, controllers 32, SIM servers 26, SIMlibrarian computing system 34, and/or SIM accounting computing system36. The computing system 39 is logically connected to one or more othercomputing systems 39 under any known method of permitting computers tocommunicate, such as through a local area network (“LAN”) 72, or a widearea network (“WAN”) including, for example, the Internet 74. Suchnetworking environments are well known including wired and wirelessenterprise-wide computer networks, intranets, extranets, and theInternet. Other embodiments include other types of communicationnetworks such as telecommunications networks, cellular networks, pagingnetworks, and other mobile networks. When used in a LAN networkingenvironment, the computing system 39 is connected to the LAN 72 throughan adapter or network interface 76 (communicative linked to the bus 43).When used in a WAN networking environment, the computing system 39 mayinclude an interface 78 and modem 80 or other device, such as thenetwork interface 76, for establishing communications over theWAN/Internet 74.

The modem 80 is shown in FIG. 2 as communicatively linked between theinterface 78 and the WAN/Internet 74. In a networked environment,program modules, application programs, or data, or portions thereof, canbe stored in the computing system 39 for provision to the networkedcomputers. In one embodiment, the computing system 39 is communicativelylinked through the LAN 72 or WAN/Internet 74 with TCP/IP middle layernetwork protocols; however, other similar network protocol layers areused in other embodiments, such as user datagram protocol (“UDP”). Thoseskilled in the relevant art will readily recognize that the networkconnections shown in FIG. 2 are only some examples of establishingcommunications links between computers, and other links may be used,including wireless links.

An operator can enter commands and information into the computing system39 through optional input devices, such as a keyboard 82, and a pointingdevice, such as a mouse 84. Other input devices can include amicrophone, joystick, scanner, etc. These and other input devices areconnected to the processing unit 40 through the interface 78, such as aserial port interface that couples to the bus 43, although otherinterfaces, such as a parallel port, a game port, or a wirelessinterface, or a universal serial bus (“USB”) can be used. A monitor 86or other display device is coupled to the bus 43 via a video interface88, such as a video adapter. The computing system 39 can include otheroutput devices, such as speakers, printers, etc.

The significant differences between the SIM server 26, controllercomputing system 32, SIM librarian computing system 34, and SIMaccounting computing system 36 are typically in the operation of thevarious computing systems 26, 32, 34, 36, as embodied the particularapplication programs, other programs/modules, program data and/oroperating system loaded in the system memory 42, and is discussed indetail below.

FIG. 3 shows the SIM bank 28, having a number of positions, for exampleslots, collectively referenced as 92 and individually referenced as 92a–92 n, sized and dimensioned for receiving SIMs, collectivelyreferenced as 94 and individually referenced as 94 a–94 n. In FIG. 2,one SIM 94 n is shown removed from the SIM slot 92 n, exposing aninterface 96 for communicatingly coupling to a complementary interfaceon the SIM 94 n. The interface 96 may, for example, take the form of anumber of electrical contacts or optical transceivers aligned tocommunicatingly couple with a complementary interface (not shown) on theSIM 94 n.

The SIM server 26 and SIM bank 28 can share a common housing asillustrated in FIG. 1 by SIM servers 26 b–26 d and associated SIM banks28 b–28 d. Alternately, the SIM server 26 may be separately housed fromthe respective SIM bank 28 as illustrated in FIG. 1 by SIM servers 26 a,26 e and associated SIM banks 28 a, 28 f, 28 g, and 28 e.

A universal asynchronous receiver/transceiver (“UART”), collectivelyreferenced as 98 and individually referenced as 98 a–98 n, is associatedwith each of the SIM slots 92 a–92 n. The UART 98 is a device, usuallyin the form of an integrated circuit, that performs theparallel-to-serial conversion of digital data that has been transmitted,for example, from a modem or other serial port, for use by a computer,and which converts parallel to serial, for example, suitable forasynchronous transmission over phone lines. While illustrated as aportion of the SIM bank 28, the UARTs 98 may be housed within the SIMserver 26.

FIG. 4 shows an example of a remote wireless communications client 16 inthe form of a remote test platform 16 c including a first and a secondwireless communications device, collectively referenced as 100 andindividually referenced as 100 a, 100 b. In the illustrated embodiment,the wireless communications devices 100 a, 100 b can take the form ofcellular telephones, with or without their individual housings, keypadsand/or displays, each of the cellular telephones including one or moreSIM interfaces 102 a, 102 b, respectively, such a SIM slots, electricalcontacts such as pins, optical transceivers or other interfaces. In someembodiments, the SIM interfaces 102 a, 102 b may be empty, the wirelesscommunications device 100 a, 100 b completely relying on remote accessto SIMs 94, while in other embodiments one or more SIM interfaces 102 cmay contain a SIM 84 for local access. The wireless communicationsdevices 100 a, 100 b wirelessly communicate via the cellular network 12.

The remote test platform 16 c includes communications switch 104 such asan audio switch which can cross-couple an input and output between thetwo wireless communications devices 100 a, 100 b. The communicationsswitch 104 can also couple audio and data signals received at one ormore physical and/or virtual ports 106 a, 106 b by way of, for example,a network 108 such as a landline network, IP network, voice-over-IPnetwork, wireless modem or wireless data communications network such asGPRS, 1XRTT to name a few, which may be the same as, or a portion of,the communications network 22 (FIG. 1). The remote test platform 16 calso includes a processor 110, which receives commands and data at aport 112 by way of the network 108. The processor 110 controls thewireless communication devices 100 a, 100 b, as described in detailbelow. The processor 110 also couples to a bridge 114 that includes acontroller such as a micro-controller 116, and a field programmable gatearray 118. The field programmable gate array 118 includes logicalinsertion UARTs 120 a, 120 b which provide information from the SIM 94,such as subscriber identity information and/or subscriber configurationinformation, in a serial stream at respective SIM interfaces 102 a, 102b.

FIG. 5 is the logical representation of the SIM server 26 and SIM bank28. SIM server 26 operates according to instructions stored in thesystem memory 42 (FIG. 2), for example, instructions stored as theoperating system 62, application program 64, other programs/modules 66,program data 68 and/or browser 70. While the above description presentsa physical embodiment of the SIM server 26, under the logical embodimenteach process, instance or session spawned by the SIM server computingsystem constitutes a separate “SIM server.” The SIM server 26 ensuresthat power and ground are applied to the various contacts of each of theSIMs 94 in the correct order.

The SIM server 26 includes a span protocol listener 130 that monitors acommunications port for requests from the remote wireless communicationsclients 16. Requests may include requests to associate a SIM 94 with awireless communications client 16, or requests to transfer informationto and/or from the SIM 94. The SIM server 26 also includes a SIM nameresolver 132 that resolves human-recognizable names into acomputer-recognizable name. The SIM server 26 further includes a numberof SIM socket control and span encapsulation threads, collectivelyidentified as 134 and individually identified as 134 a–134 d. Theinstances of SIM socket control and span encapsulation threads providevarious remote wireless communications clients 16 with access to the SIMinformation from the various SIMs 94, such as subscriber identityinformation and/or subscriber configuration information viabi-directional communications.

The SIM server 26 includes a configuration and control user interface136 to handle interactions with the various wireless communicationsclients 16. The configuration and control user interface 136 allows theSIM server 26 to receive requests and to respond to such requests witheither the requested SIM information or with an address for retrievingthe requested SIM information.

The SIM server 26 includes a group protocol manager 138 which handlesthe interaction between SIM servers 26 in a group, such as SIM servers26 b, 26 c, 26 d of the SIM server group 30 b (FIG. 1). For example, thegroup protocol manager 138 allows the interchange of SIMlocation/identification information between the various SIM servers 26b, 26 c, 26 d of the SIM server group 30 b. Thus, all SIM servers 26 inthe SIM server group 30 have up-to-date information about the SIMs 94 inall of the SIM banks 28 associated with the SIM servers 26 included inthe particular SIM server group 30.

The SIM server 26 includes a library protocol manager 140 that controlsinteraction with the SIM librarian computing system 34. This allows anyone of the SIM servers 26 to locate SIMs 94 in SIM banks 28 associatedwith other SIM servers 26 that are not included within the same SIMserver group 30 as the inquiring SIM server 26.

FIG. 6 shows a logical representation of the remote wirelesscommunications client 16 in the form of a remote test platform 16 c. Theprocessor 110 provides client entity services 150. The processor 110also provides a span encapsulation engine 152 for handling theinteraction between the processor 110 and the bridge 114, for examplecreating and/or opening envelopes including packets of data such as SIMinformation. The processor 110 employs a transport 154 between theclient entity services 150 and a command interface 156 which may bemanual and/or automated. The command interface 156 interacts with ageneral interface 158 a, 158 b which is a logical function of thewireless communications devices 100 a, 100 b, respectively.

FIG. 7 shows a logical view of the SIM librarian computing system 34having instructions stored in the system memory 42 for tracking networkaddresses of particular SIMs 94 and providing the network addresses inresponse to queries. The SIM librarian computing system 34 includes apersistent name list storage 160 which may, for example, take the formof a data structure 338 (FIG. 12) stored in system memory 42. The datastructure 338 may include one or more human-recognizable names for theSIM 94 (FIG. 3), a network address for the SIM 94 including an addressof a SIM server 26 (FIG. 1) having access to the SIM bank 28 holding theSIM 94. The data structure 338 may further include additionalinformation such as geographic location of the SIM 94 and/or adescription of the contents of the SIM 94 including SIM information suchas the subscriber identification information (e.g., ISMI) and/orsubscriber configuration information, as discussed in detail below withreference to FIG. 12.

The SIM librarian computing system 34 also includes a name listmanagement user interface 162. The name list management user interface162 handles the maintenance of the persistent name list storage 160, forexample creating, modifying and/or deleting information from thepersistent name list storage 160.

The SIM librarian computing system 34 further includes a libraryprotocol 164 which allows SIM servers 26 to access information in thepersistent name list storage 160. The library protocol 164 may furtherallow the SIM librarian computing system 34 to pass inquiries to the SIMservers 26, for example, to verify existing information in thepersistent name list storage 160, and/or receive new and updatedinformation from the SIM servers 26 for use in maintaining thepersistent name list storage 160. In use, a remote wirelesscommunications client 16 connecting to any SIM server 26 a, 26 e not inthe SIM server group 30 b (FIG. 1) will effectively search every server26 a, 26 e not in the SIM server group 30 b with a single request. Toquery the SIM servers 26 b–26 d in the SIM server group 30 b requires aseparate connect sequence. Thus, to scan every SIM server 26 a–26 e, aremote wireless communications client 16 would have to have only twoservers saved in its configuration files.

Operating a Wireless Communications Client

FIG. 8 shows a method 200 of operating a wireless communications client16 according to one illustrated exemplary embodiment. In step 202, thegeneral computer 110 (FIG. 6) of the wireless communications client 16monitors one or more communications ports 106, 112 (FIG. 4). Asdiscussed above, the communications ports may take the form of physicalport and/or virtual ports. The flow of data and or commands between thewireless communications client 16 and other system components areillustrated by large arrows pointing into and away from the variousboxes which represent the acts and steps of the method. A similarconvention is employed in the Figures illustrating other methods ofoperation of the SIM remote access system 24.

In step 204, the wireless communications client 16 receives a requestfor a SIM 94, for example, from one of the controllers 32 (FIG. 1). Therequest may include a unique SIM identifier and/or a human-recognizablename corresponding to the SIM 94 or group of SIMs 94. In step 206, thewireless communications client 16 sends a request for the SIM 94 to aSIM server 26. In step 208, the wireless communications client 16determines whether an address is received from the SIM server 26. If anaddress is received in step 208, the wireless communications client 16sends another request in step 210, this request being sent to an addressreturned by the SIM server 26. In step 211, the wireless communicationsclient 16 receives connection information from the SIM server 26 towhich the request was addressed in either step 206 or 210.

In step 212, the general purpose computer 110 employs the bridge 114 toassociate one the wireless communications device 100 of the wirelesscommunications client 16 with the subscriber information from the SIM 94by establishing a communications session between the wirelesscommunications device 100 and the SIM 94. The communications session mayemploy a socket protocol for establishing a persistent communicationssession, lasting until the SIM 94 is explicitly released.

With a persistent communications session started, in step 213 thewireless communications client 16 determines whether a command isreceived, for example, from the controller 32. If a command has beenreceived, in step 214 the wireless communications client 16 determineswhether the command is to release the SIM 94. If the command is not torelease the SIM 94, the wireless communications client 16 employs thecommand interface 156 to execute the command in step 215, operating thewireless communications device 100 via the general interface 158, themethod 200 then retuning to step 213. If the command is to release theSIM 94, in step 216 the wireless communications client 16 employs theclient entity services 150 to release the SIM 94, for example, bysending an appropriate message to the SIM server 26 and terminating thecommunications session with the SIM 94 via the span encapsulation engine152.

In step 218, the wireless communications device 16 determines whether arequest is received, for example, from the MSC 20. As discussed in thebackground, the MSC 20 may, from time-to-time, request certaininformation from the SIM 94, including challenging the SIM 94 with anauthentication request. Under the GSM standard the authorization requestincludes a random number or seed. If a request has not been received,the method 200 returns to step 213. If a request has been received, thewireless communications client 16 employs the span encapsulation engine152 to pass the request to the SIM 94 via the communications session instep 220.

In step 221, the wireless communications client 16 determines whether aresponse is received from the SIM 94, transmitting wait signals back tothe requester (e.g., MSC 20) in step 222 where required to prevent atime out from occurring. Often, the MSC 20 or other portion of thewireless service provider system will require a response from thewireless communications client 16 within a specified time period. Step222 provides a “wait” message to the MSC 20 or other portion of thewireless service provider system. In some instances, successive “wait”messages can provide a sufficient response, although some wirelessservice provider systems will limit the number of consecutive “wait”messages that may be received before terminating the connection. The“wait” loop repeats until the wireless communications client 16 receivesa response from the SIM 94, at which point control passes to step 223.Once a response is received from the SIM 94, the wireless communicationsclient 16 passes the response to the requester (e.g., MSC 20) in step223, and returns to step 213.

It should be noted that the wireless communications device 16 is capableof handling multiple communications sessions at the same time, forexample, the wireless communications device 16 may simultaneously behandling a separate communications session for each of the wirelesscommunications clients 100 a, 100 b. Thus, the wireless communicationsdevice 16 continues monitoring the communications port (i.e., step 202),while executing other portions of the method 200. The general computer110 of the wireless communications client 16 may employ a multitaskingstrategy, multiple processors or other techniques to realize suchconcurrent operation.

Operating a SIM Server

FIGS. 9A and 9B show a method 250 of operating a SIM server 26 accordingto one illustrated exemplary embodiment.

In step 251, the span protocol listener 130 (FIG. 5) of the SIM server26 monitors a communications port. In step 252, the SIM server 26receives a request from a remote wireless communications client 16. Therequest may originate with the remote wireless communications client 16,or may originate with the controller 32.

In optional step 253, the SIM server 26 determines whether the requestincludes sufficient authorization to provide access to the requested SIMinformation. Authorization can take any one or more of a variety offorms. For example, the request can include one or more user identifiersand/or passwords generated by one or both of the controller 32 and therequesting wireless communications client 16. The user identifier may beassociated with a privilege level, allowing certain types of access tocertain SIMs 94. Alternatively, or additionally, the request may containan indication of a business, tracking or billing entity making therequest. This information can be compared with SIM ownership informationstored in the requested SIM 94 and/or stored locally at the SIM server26 for allowing authorization determinations without inquiries to theSIM 94. Thus, in some embodiments the SIM server 26 may read informationfrom the requested SIM 94 in order to determine whether the requestincludes sufficient authority, while in other embodiments the SIM server26 makes the determination without resort to the requested SIM 94,relying on pre-stored information or on a level of authority that is notspecific to the particular SIM 94. Consequently, it should be clear toone skilled in the art that the optional step 253 may occur at otherpoints in the method 250.

If the request does not include sufficient authorization, the SIM server26 denies the request in step 254, perhaps passing an appropriatemessage to the requesting wireless communications device 16 and/orcontroller 32. The method 250 then returns to a “wait” state, monitoringthe communications port in step 251. Additionally, or alternatively, theSIM server 26 may track the number of unauthorized requests for the SIM94, or may track the number of unauthorized requests by the particularrequesting wireless communications client 16, to deter unauthorizedentries. If the request does include sufficient authorization, the SIMserver 26 passes control to step 255.

In step 255, the SIM name resolver 132 (FIG. 5) of the SIM server 26determines whether a received human-recognizable name for the SIM 94 isresolvable. If the name is not resolvable, the method 250 passes controlto step 269 where a request is sent to the SIM librarian 34, details ofwhich are explained below. If the human-recognizable name is resolvable,the SIM name resolver 132 resolves the human-recognizable name into acomputer-recognizable or computer-routable name in step 256.

In step 257, the SIM server 26 determines whether the requested SIM 94is accessible by the SIM server 26. SIMs 94 are considered accessible bythe SIM server 26 if the SIM server 26 can read, write and/or commandthe SIM 94, for example where the SIM 94 is in a SIM bank 28 associatedwith the SIM server 26. If the requested SIM 94 is accessible by the SIMserver 26, in step 258 the SIM server 26 determines whether therequested SIM 94 is available for use. If the requested SIM 94 isavailable, in step 261 the SIM server 26 exclusively associates therequested SIM 94 with the requesting wireless communications client 16.For example, the SIM server 26 may establish a persistent communicationssession between the requested SIM 94 and the requesting wirelesscommunications client 16. Additionally, or alternatively, the SIM server26 may set a flag in the SIM 94 and/or identify the SIM 94 as beingexclusively allocated or “not available” in a corresponding databasewhich the SIM server 26 checks as part of step 258 and/or step 259(discussed immediately below). The SIM server 26 may retain theexclusive association between the requested SIM 94 with the requestingwireless communications client 16 until the SIM server 16 receives arequest to release or terminate the association, or until a “time-out”condition occurs.

If the requested SIM 94 is not available, the SIM server 26 sends anappropriate message to the requesting wireless communications device 16and/or controller 32 indicating that the SIM 94 is not available for usein optional step 259, and then returns to the “wait” state, monitoringthe communications port in step 251.

If the requested SIM 94 is available, the method 250 passes control tostep 260. In step 260, the SIM server exclusively associates therequested SIM 94 with the remote wireless communications device 100, anillustrated example of which is described below with reference to FIG.9C.

Returning to step 257, if the SIM server 26 determines the requested SIM94 is not accessible by the SIM server 26, the method 250 passes controlto step 261, where the SIM server 26 determines whether the requestedSIM 94 is accessible by other SIM servers 26 in a same SIM server group30.

If the requested SIM 94 is accessible by another SIM server 26 in thesame SIM server group 30, the SIM server 26 provides address informationfor the requested SIM 94 to the requesting remote wirelesscommunications client 16 in step 262, and then returns control to step252. If the requested SIM 94 is not accessible by other SIM servers 26in the same SIM server group 30, the SIM server 26 sends a request tothe SIM librarian system 34 in step 263.

In step 264, the SIM server 26 receives a response including an addressfrom the SIM librarian 34. In step 265, the SIM server 26 returns thereceived address to the requesting remote wireless communications client16, and returns to a waiting state at step 252.

FIG. 9C shows an exemplary illustrated method 266 of exclusivelyassociating the requested SIM 94 with the wireless communications device100 of the requesting wireless communications client 16. The method 266is suitable for realizing the step 260 of the method 250 (FIGS. 9A, 9B).

In step 267, the SIM server 26 exclusively reserves the SIM 94, forexample marking the SIM 94 as being unavailable in an appropriatedatabase or otherwise ensuring that the SIM 94 is not available for useby other requesters. In step 268, the SIM server 26 provides connectioninformation to the requesting remote wireless communications client 16and employs the SIM socket control 134 to start up a local protocol andwaits for a connection. In step 269, the SIM server 26 starts the localspan protocol instance (e.g., span encapsulation thread 134134 d)associated with the requested SIM 94. In step 270, the SIM server 26receives a communication from the remote wireless communications client16. In step 271, the SIM server 26 determines whether the requestcorresponds to a request to release the SIM 94 or otherwise close theconnection.

If the request is to release the SIM 94 or otherwise close theconnection, in step 272 the SIM server 26 stops the local span protocolinstance 134 a–134 d associated with the SIM 94. In step 273, the SIMserver 26 then makes the SIM 94 available, for example, marking the SIM94 as being available in the appropriate database. In step 274, the SIMserver 26 returns a message to the remote wireless communications client16 indicating that the connection has been closed and the exclusiveassociation has been terminated.

If the SIM server 26 determines in step 271 that the request does notcorrespond to a request to release the SIM 94 or otherwise close theconnection, in step 275 the SIM server 26 removes a protocol wrapper andpasses the payload data of the request to the SIM 94. In step 276, theSIM server 26 receives a response from the SIM 94. In step 277, the SIMserver 26 wraps the payload data (i.e., received response) into anencapsulation protocol and transmits the encapsulated payload data tothe wireless communications device 100 of the wireless communicationsclient 16. The method 266 then returns to step 270 for receipt offurther communications from the wireless communications client 100.Typical SIMs 94 are not capable of initiating action, but rather canrespond to requests to retrieve and/or store information or to performother actions.

FIG. 9D shows an exemplary illustrated method 278 of passing anauthorization challenge and response between a wireless communicationsdevice 100 of the wireless communications client 16 and a SIM 94, inaccordance with the method 266 (FIG. 9C). In at least some embodiments,the SIM server 26 may be unaware of the contents of some or all of therequests or communications, and will simply be forwarding communicationsbetween the wireless communications device 100 and the SIM 94. Thus, theSIM server 26 may be unaware that it is transmitting an authorizationchallenge and response.

In step 279, the SIM server 26 passes an authorization request receivedvia the wireless communications client 16 to the SIM 94. As discussed inthe background, it is common for the MSC 20 or other portion of thewireless service provider system to periodically challenge the wirelesscommunications device 100 for authentication. This prevents fraud, forexample by preventing the simultaneous use of a subscriber identity bythe swapping of a single SIM 94 between multiple wireless communicationsdevices 100 after starting a call on each of the respective wirelessdevices 100. Under GSM, the challenge or authentication request includesa random number or seed, which the SIM 94 employs along with the secretkey encoded in the SIM 94 to algorithmically create a response, commonlyreferred to as a “signed response.”

In step 280, the SIM server 26 receives a response from the SIM 94. Instep 281, the SIM server 26 provides subscriber information in the formof the response from the requested SIM 94 to the requesting remotewireless communications client 16.

Additionally, the SIM server 26 may cache certain data to decrease thetime the SIM server 26 takes to respond to requests. For example, theSIM server 26 may be programmed to store the first response from a SIM94 to each of a number of selected requests (e.g., SS7 messages or othercommunications) in a data cache. The requests may be selected by thestability of the response and/or the frequency with which the particularrequest occurs in typically transactions. Further, the SIM server 26 canbe programmed to “learn” which requests/response combinations to cacheby recognizing patterns of requests (e.g., SS7 messages) and responses,for example relying on the stability of the response and the frequencyof the request during operation. Thus, the SIM server 26 does not evenneed to understand or know what is being requested, but simply mustunderstand if the requested data is stable or changes over time. Wherethe caching is bi-directional (i.e., retrieval from, and storage to, theSIM 94), the SIM server 26 may also store a direction indication in thedata cache. One skilled in the art will note that caching typically willnot work for authorization challenges, since the correct response isdependent on a random number or seed provided with each authorizationrequest. However, caching can significantly reduce response times forthe retrieval and/or storage of other information, which may beparticularly useful where a portion of the communications network 22employs TCP/IP with its associated timing problems.

FIG. 18 shows one illustrated embodiment of a method 550 for operatingthe SIM sever 26 employing caching. The method 550 may be employed aspart of, or as a substitute for, the method 250 of FIG. 9.

In step 552, the SIM server 26 receives a request for the SIM 94 fromthe wireless communications client 16. In step 554, the SIM server 26determines whether a response to the request has been cached in the datacache. If the response to the request has been cached, in step 556 theSIM server 26 retrieves the cached response, passes the retrieved cachedresponse to the wireless communications client in step 558, and returnsto step 552. Thus, the SIM server can provide the response to therequester, either directly where the requester is the wirelesscommunications client 16 or indirectly via the wireless communicationsclient 16 where the requester is the MSC 20, without the delayassociated with passing the request to the SIM 94 and waiting for aresponse from the SIM 94. This can provide significant saving in latencyand response times.

If the response to the request has not been cached, in step 560 the SIMserver 26 passes the request to the SIM 94. In step 562, the SIM server26 receives a response from the SIM 94. In step 564, the SIM server 26passes the response received from the SIM 94 to the wirelesscommunications client 16.

In step 566, the SIM server 26 determines whether there is arelationship between the received response and the request. As discussedabove, the SIM server 26 can determine whether the request of a typepreviously identified as being suitable for caching, or can analyze thestability of the response and/or frequency of the request in determiningif a relationship exists. The SIM server may rely on a set ofrelationship recognition information which may include a list ofrequests suitable for caching, a tracking of the number of times aparticular response has occurred for a given request, and/or acumulative tally of the number of times or frequency that particularrequests have occurred.

If the SIM server 26 determines that there is a relationship, the SIMserver 26 caches the response in the data cache in step 568, and returnsto step 552 to wait for the next request. As an alternative, the SIMserver 26 may pass control to step 570 before returning to step 552.

If the SIM server 26 determines that there is a no relationship, the SIMserver 26 updates a set of relationship recognition information in step570 and returns to step 552 to wait for the next request.

Operating a SIM Librarian

FIG. 10 shows a method 300 of operating a SIM librarian computing system34 according to one illustrated exemplary embodiment. In step 302, theSIM librarian computing system 34 waits for a request on acommunications port. In step 304, the SIM librarian computing system 34receives a request for SIM address from a SIM server 26. In step 306,the SIM librarian computing system 34 resolves the human-recognizableSIM identifier in the received request into a computer-recognizable SIMidentifier. The human-recognizable SIM identifier can take any of avariety of forms such as a name of the SIM 94, group of SIMs 94, and/orcharacteristic of the SIM 94 (e.g., geographic location, home callingarea, wireless communications service provider, phone type, etc.). Instep 308, the SIM librarian computing system 34 determines an addressfor the requested SIM 94 based on the computer-recognizable SIMidentifier. In step 310, the SIM librarian computing system 34 returnsthe determined address for the requested SIM 94 to the requesting SIMserver 26. SIM librarian computing system 34 returns control to step302, waiting for additional requests.

Maintaining a Persistent Name List

FIG. 11 shows a method 320 of maintaining SIM information in apersistent name list storage 160 (FIG. 7) of the SIM librarian computingsystem 34 according to one illustrated exemplary embodiment.

In optional step 322, the SIM librarian computing system 34 transmits aninquiry to one or more of the SIM servers 26. In step 324, the SIMlibrarian computing system 34 receives SIM location and/oridentification information from the SIM servers 26. In step 326, the SIMlibrarian system 34 determines whether the received SIMlocation/identification information identifies a new SIM being added toa SIM bank.

If a new SIM 94 is being added to a SIM bank 28, the SIM librariancomputing system 34 creates a corresponding new entry in a datastructure 338 (FIG. 12) stored in the persistent name list storage 160,and the method 320 returns control to step 322. Otherwise, the SIMlibrarian computing system 34 determines whether a SIM 94 is deleted orremoved from one of the SIM banks 28 in step 330. If a SIM 94 is beingdeleted or removed, the SIM librarian computing system 34 deletes acorresponding entry from the data structure 338 (FIG. 12) stored in thepersistent name list storage 160 in step 332, the method 320 thenreturning control to step 322. If a SIM 94 is not being deleted, the SIMlibrarian computing system 34 determines whether the SIMlocation/identification information for a SIM has changed in step 334.

If the SIM location/identification information has changed, the SIMlibrarian computing system 34 updates a corresponding entry in the datastructure 338 (FIG. 12) and the persistent name list storage 160 in step336, the method 320 then returning control to step 322. Otherwise themethod 320 passed control directly to step 322. Typically the locationor human-recognizable identification information may change, while theunique SIM identifier will remain unchanged.

Data Structure for SIM Information

FIG. 12 shows a data structure 338 including a number of records,collectively referenced as 340 and individually referenced as 340 a–340c, for storing SIM location/identification information in the persistentname list storage 160 (FIG. 7) of the SIM librarian computing system 34.Each record 340 includes a number of fields, for storing informationabout the SIM 94 including human-recognizable information to simplifythe task of SIM selection. The fields represented in FIG. 12 areexemplary, and the records 340 may include a greater or a lesser numberof fields, and/or other fields.

A “SIM serial number” field 342 stores a SIM serial number for uniquelyidentifying the SIM 94. A number of “SIM name” fields 344, 346 storehuman-recognizable names for the SIMs. There may be a less or greaternumber of “SIM name” fields, although only two are shown. The SIMs 94may be randomly assigned names, or given names based on some property ofthe SIM such as physical location of the SIM 94 or of the home callingarea associated with the SIM 94.

A number of “SIM group” fields 348, 350, 352 store group identifierswhich identify one or more groups to which the SIM 94 belongs. Groupingof SIMs 94 allows easy access to SIMs 94 with similar characteristics orusefulness. A “SIM server group” field 354 stores an identifier of a SIMserver group 30 to which the SIM 94 is associated by way of beingreceived in a SIM bank 28 associated with one of the SIM servers 26 thatbelong to the SIM server group 30. A “SIM server address” field 356stores a computer-routable address for the SIM server 26 to which theSIM 94 is associated. A “SIM bank identifier” field 358 stores acomputer-routable address, such as a port number, of the SIM bank 28 inwhich the SIM 94 is received. The “SIM position” field 360 stores acomputer-routable address, such as a slot number, corresponding to aposition 92 of the SIM bank 28 in which the SIM 94 is received.

A “SIM logical geographic location” field 362 stores an indication of alogical geographic location for the SIM 94. A “SIM physical geographiclocation” field 364 stores an indication of a physical geographiclocation of the SIM 94, for example a city in which the SIM bank islocated. A “SIM associated carrier” field 366 stores an identificationof a wireless communications provider or carrier with which the SIM 94is associated. For example the SIM 94 may be associated with aparticular wireless service provider. A “carrier service plan” field 368stores an indication of the particular carrier service plan with whichthe SIM 94 is associated. For example the SIM 94 may be associated witha particular unlimited long distance plan of a particular carrier.

A “home area” field 370 includes an indication of a particular homecalling area with which the SIM 94 is associated. Home calling areas arecommon in cellular calling plans. A “subscriber configuration”description field 372 includes a description of various configurationparameters for the wireless communications device 16 which arepreprogrammed into the SIM 94. For example, the SIM 94 may store a listof frequently used telephone numbers which are automatically programmedin the wireless communications device 16 when associated with aparticular SIM 94, a font for use in a display menu, or a notificationsetting such as ring, vibrate or ring and vibrate.

A “SIM owner” field 374 may identify a person or entity that owns theSIM 94. For example, the owner could be one of a number of billingentities such as a company, or a department within a company, which maybe particularly useful to the SIM accounting computing system 36 (FIG.1). The “SIM owner” field 374 allows an operator to elect to employ SIMs94 that the operator owns, before relying on SIMs 94 for which theoperator would have to receive permission and/or pay a fee to use.

Operating SIM Accounting System

FIGS. 13A and 13B show a method 400 of accounting for SIM usageaccording to one illustrated exemplary embodiment. Most of the steps inthe method 400 are optional, and are dependent upon the particularinformation that interests an operator of the SIM remote access system24. Additionally, many of the steps can be executed in a differentorder, and additional steps may be added to the method 400.

In step 402, the SIM accounting computing system 36 (FIG. 1) receivesusage information for a SIM 94, for example from the SIM server 26 withwhich the SIM 94 is associated and/or from a wireless communicationsclient 16 requesting or using the SIM 94. In step 404, SIM accountingcomputing system 36 increments a cumulative count of the number of timesthat the SIM 94 has been accessed. In step 406, the SIM accountingcomputing system 36 increments a cumulative count of the number of timesthat the SIM 94 has been accessed by a particular billing entity. Instep 408, the SIM accounting computing system 36 increments a cumulativecount of the number of times the billing entity has accessed any of theSIMs 94 available via the SIM remote access system 24.

In step 410, the SIM accounting computing system 36 determines from thereceived SIM usage information the amount of time that the SIM 94 hasbeen accessed. In step 412, the SIM accounting computing system 36 addsthe determined amount of time that the SIM 94 has been accessed to acumulative amount of time that the SIM 94 has been accessed. In step414, the SIM accounting computing system 36 adds the determined amountof time that the SIM 94 has been accessed to a cumulative amount of timethat the SIM 94 has been accessed by a billing entity for theappropriate billing entity. This permits the SIM accounting computingsystem 36 to track the total amount of usage of a particular SIM 94 by aparticular billing entity. In step 416, the SIM accounting computingsystem 36 adds the determined amount of time that the SIM 94 has beenaccessed to a cumulative amount of time that the billing entity hasaccessed all SIMs 94 for the appropriate billing entity.

In step 418, the SIM accounting computing system 36 determines theperiod of access to the SIM 94. For example, a day may be divided intodifferent periods which may have different accounting aspects, forexample different rates dependent upon predicted demand for the period.In a similar fashion a week, month or year may be divided into differentperiods, for example weekend SIM usage may be associated with a lowerrate than weekday SIM usage.

In step 420, the SIM accounting computing system 36 adds the determinedamount of time that the SIM 94 has been accessed to a cumulative amountof time that the SIM 94 has been accessed during the period for theappropriate period. In step 422, the SIM accounting computing system 36adds the determined amount of time that the SIM 94 has been accessed toa cumulative amount of time that the SIM 94 has been accessed by thebilling entity during the period for the appropriate period and billingentity. This allows the SIM accounting computing system 36 to track abilling entity's usage of a SIM 94 by period, which may be particularlysuitable for some billing scenarios. In step 424, the SIM accountingcomputing system 36 adds the determined amount of time the SIM 94 hasbeen accessed to a cumulative amount of time the billing entity hasaccessed all SIMs during the period for the appropriate billing entity.

In step 426, the SIM accounting computing system 36 determines the costof access to the SIM 94. In step 428, the SIM accounting computingsystem 36 adds the determined cost of access to the SIM 94 to acumulative amount of cost for access to the SIM 94. In step 430, the SIMaccounting computing system adds the determined cost of access to theSIM 94 to a cumulative amount of cost for access to the SIM 94 by aparticular billing entity during the period for an appropriate periodand billing entity. In step 432, the SIM accounting computing system 36adds the determined cost of access to the SIM 94 to a cumulative amountof cost for access to all SIMs 94 by the billing entity for theappropriate billing entity. In step 434 the SIM accounting computingsystem 36 bills the billing entity for the billing entity's SIM usageduring the billing period.

FIG. 14 shows a method 440 of accounting for SIM usage which may beemployed in addition to, or in substitution to, step 434 of FIGS. 13A,13B.

In step 442, the SIM accounting computing system 36 subtracts thecumulative cost from a billing entity balance that represents a sum offunds on account for the billing entity or a credit to an billing entityaccount. For example, the billing entity may receive a set balance inits accounts for a regular monthly payment. Usage exceeding theallocated amount may be billed by time, for example, by each wholeminute, rounded up. While the account balance is discussed in terms ofcost, one skilled in the art will recognize that the cost and accountscan just as easily be represented in terms of time or number of uses.

In step 444, the SIM accounting computing system 36 determines if thebalance is below some set minimum balance. If the balance is not belowthe set minimum balance, the SIM accounting computing system 36 grantsfurther access to SIMs in step 446. If the balance is below the minimumaccess, the SIM accounting computing system 36 may optionally offer anopportunity to replenish the balance in step 448. For example, the SIMcomputing accounting system 36 may allow a user (e.g., billing entity)to enter a charge account number, or prepaid card number to replenishthe balance of the account.

In step 450, the SIM accounting computing system 36 determines if thebalance is replenished. If the balance has been replenished, the SIMaccounting computing system 36 grants further access to the SIMs 94 instep 446. If the balance has not been replenished, the SIM accountingcomputing system 36 denies further access to the SIMs 94 in step 452.

Wireless Communications Device Server

FIG. 15 shows a wireless communications device remote access system 500,in use with the remote SIM access system 24 of FIG. 1. The wirelesscommunications device remote access system 500 includes a wirelesscommunications device rack 502 having a number of positions forreceiving proxy wireless communications devices and a proxy wirelessdevice server 503 capable of communicatively coupling proxy wirelesscommunications devices received in the rack 502 to controllers 32,controlling wireless communications clients 16, and/or controllingwireless communications devices 100 (FIG. 4). The wirelesscommunications device remote access system 500 can also include awireless device usage accounting computing system 504 and/or a wirelessdevice librarian system (not shown).

FIG. 16 shows the wireless communications device rack 502 containing thenumber of proxy wireless communications devices, for example wirelessPDAs, collectively referenced as 506 and individually referenced as 506a–506 h. As used herein and in the claims, the term proxy refers to adevice that may act as a servant or agent of another device, for examplebeing remotely controlled by the other device. The rack 502 includes abus 508 coupling the wireless PDAs 506 to a communications port 510, anda controller such as a micro-controller 512 for controlling the bus 510and/or the PDAs 506.

The rack 502 may be associated with one or more proxy wireless deviceservers 503 at a local or a central location to form the wirelesscommunications device remote access system 500. The proxy wirelessdevice servers 503 can be configured to selectively couple a wirelessPDA 506 to a remote controlling device such as a controller 32 or acontrolling wireless communications client 16 such as the remote testplatform 16 c, by way of the communications network 22.

This allows the wireless PDA 506, or other wireless communicationsdevice, to be operated as if it were present at the remote site 18 cwhere the remote test platform 16 c is located. Thus, for example, awireless device manufacturer or wireless service provider can verifythat a wireless communications device 506 is operable in a givenlocation 18 c, for example, before releasing the wireless communicationsdevice 506 for sale. This testing may be instead of, or in addition to,the previously discussed testing of switching in the remote locations18.

Additionally, or alternatively, this arrangement can allow an end userat a remote location 18 a to use a wireless communications device 506 oftheir choice without actually owning the wireless communications device506. For example, an end user may rent or lease use of a wireless PDA506, which is accessed via the end user's cellular phone 16 a or othercontrolling wireless communications device. The end user may select anyavailable wireless communications device 506 in the rack 502, or anavailable wireless communications device 506 may be automaticallyassigned to the user, for example, upon connection. Thus the remote testplatform 16 c, or other controlling wireless device, acts like thewireless PDA at the remote location, downloading files, moving data,playing games, executing networking operations and/or reporting results.

Usage and billing may be maintained by the wireless communicationsdevice accounting system 504 in a similar fashion to that of the SIMaccounting computing system 36 (FIG. 1) previously discussed. Whileillustrated in use with the SIM remote access system 24, the wirelessdevice remote access system 500 can operate independently thereof whereremote access to SIMs 94 (FIG. 3) is not required. Additionally, awireless device librarian (not shown) can operate in a similar manner tothe SIM librarian 34 previously discussed, tracking the location ofvarious proxy wireless communications devices 506 and allowing thelocation of proxy wireless communications devices 506 usinghuman-recognizable identifiers such as names.

FIG. 17 shows a method 520 operating the wireless communications deviceremote access system 500 of according to one illustrated embodiment.

In step 522, the wireless communications device server 503 receives arequest for remote access to a proxy wireless communications device 506.The request may originate from an operator of the controller 32 a, froman automatically executed script on the controller 32 a, or from anothersource, such as one of the wireless communications clients 16.

In step 524, the wireless communications device server 503 or themicro-controller 512 determines if the request was for a specific proxywireless communications device 506. If the request is not for a specificproxy wireless communications device 506, in step 526 the wirelesscommunications device server 503 or the micro-controller 512 locates anavailable proxy wireless communications device 506 in the rack 502. Ifthe request is for a specific proxy wireless communications device 506or for a proxy wireless communications device having one or morespecific characteristics (e.g., device type, user configuration, etc.),in step 528 the wireless communications device server 503 or themicro-controller 512 identifies a suitable proxy wireless communicationsdevice 506 in the rack 502.

In step 530, the wireless communications device server 503 or themicro-controller 512 determines whether the proxy wirelesscommunications device 506 is available for use. If the proxy wirelesscommunications device 506 is not available, the wireless communicationsdevice server 503 or the micro-controller 512 notifies the requester ofthe unavailability in step 532. The wireless communications deviceserver 503 or then micro-controller 512 may wait a determined period oftime in step 534, rechecking the availability one or more times beforenotifying the requester. Alternatively, or additionally, the wirelesscommunications device server 503 or the micro-controller 512 may notifythe requester in step 534 and then monitor the availability of desiredproxy wireless communications device 506 in step 536, automaticallynotifying the requester and/or automatically linking the proxy wirelesscommunications device 506 to a remote controlling wirelesscommunications client 16 in step 538 when the proxy wirelesscommunications device 506 becomes available.

If the proxy wireless communications device 506 is available (eitherfrom step 530 or step 536), the wireless communications device server503 or the micro-controller 512 determines whether the requester isauthorized to use the proxy wireless communications device 506 in step533. Authorization may include verification of one or more of a useridentifier, password, requesting device identifier, level of privilege,account balance, etc. The verification can be similar to that discussedabove with respect to authorization of SIM usage.

If the requester is not authorized, the wireless communications deviceserver 503 or the micro-controller 512 deny access to the proxy wirelesscommunications device 506 in step 535. If the requester is authorized,the wireless communications device server 503 or the micro-controller512 links the proxy wireless communications device 506 to a remotecontrolling wireless communications client 16 in step 540.

Remote Access Wired Access

FIG. 19 shows an illustrated embodiment of a remote access system 600,that can provide remote access for communication devices withoutwireless functionality such as conventional PDAs 602. The system 600 mayalso provide remote access for communication devices that have wirelessfunctionality without making use of that functionality, or making use oflimited wireless functionality such as infrared communications.

The PDA 602 typically includes a communications port 604, for example anRS232 port, for providing bi-directional communications. The PDA 602 iscoupled to a networking device such as a computer 606, to providenetworked communications via the communications network 22. The computer606 may take the form of a conventional networked PC. The coupling maytake the form of a cable or limited range communications device such asan infrared transceivers or short range wireless transceiver. A computer606 appropriately configured for the desired protocol and security canprovide access to any of the wireless communications devices 100 of thewireless communications clients 16. Thus, a user at one location mayoperate the PDA 602 as if the PDA 602 was physically present at anotherlocation, for example, the physical location of the wirelesscommunications client 16. Additionally, the wireless communicationsclient 16 may be associated with a SIM 94 located at a third physicallocation.

The connection between the PDA 604 and the computer 606 can be made inthe conventional fashion. The PC 606 simply makes the network connectionto the desired wireless communications client 16, automaticallyproviding the appropriate protocol to the communications including anyrequired handshaking and/or security.

Further Variations

The above description sets out a SIM remote access system and a wirelessdevice remote access system, and methods for each. Although specificembodiments of, and examples for, the invention are described herein forillustrative purposes, various equivalent modifications can be madewithout departing from the spirit and scope of the invention, as will berecognized by those skilled in the relevant art.

The teachings provided herein of the invention can be applied to otherremote access systems, not necessarily the SIM remote access system 24and wireless communications device remote access system 500 generallydescribed above. For example, the SIM remote access system 24 and/or andwireless communications device remote access system 500 may include agreater or less number of computing systems, for example eliminating theSIM accounting computing system 36 and/or the SIM librarian computingsystem 34. The SIM accounting system 24 and/or and wirelesscommunications device remote access system 500 can include a greater orless number of remote communications clients 16. While illustrated inFIG. 12 as a set of records 340 having fields, the data structure 338can take a variety of other forms commonly employed in the computingarts, including but not limited to one or more linked lists, lookuptables or the like. Additionally, many of the methods include optionalacts or steps, and may include additional act or steps, or perform thesteps in a different order, as will be recognized by those skilled inthe relevant arts.

The SIM remote access system 24 and/or wireless communications deviceremote access system 500 can have a different organization than theillustrated embodiment, combining some functions and/or eliminating somefunctions. The system 24 can employ some of the disclosed automatedcomponents for some functions, while relying on manual methods for otherfunctions. The system can be more centralized, or more distributed, asis suitable for the particular communications environment.

The various embodiments described above can be combined to providefurther embodiments. All of the above U.S. patents, U.S. patentapplication publications, U.S. patent applications, foreign patents,foreign patent applications and non-patent publications referred to inthis specification and/or listed in the Application Data Sheet areincorporated herein by reference in their entirety, including but notlimited to commonly assigned U.S. provisional patent application Ser.No. 60/379,603, entitled “METHOD, APPARATUS AND ARTICLE TO REMOTELYASSOCIATE WIRELESS COMMUNICATIONS DEVICES WITH SUBSCRIBER IDENTITIESAND/OR PROXY WIRELESS COMMUNICATIONS DEVICES,” filed May 9, 2002.Aspects of the invention can be modified, if necessary, to employsystems, circuits and concepts of the various patents, applications andpublications to provide yet further embodiments of the invention.

These and other changes can be made to the invention in light of theabove-detailed description. In general, in the following claims, theterms used should not be construed to limit the invention to thespecific embodiments disclosed in the specification and the claims, butshould be construed to include all SIM remote access systems and methodsthat operate in accordance with the claims. Accordingly, the inventionis not limited by the disclosure, but instead its scope is to bedetermined entirely by the following claims.

1. A system to remotely operate wireless communications devices, thesystem comprising: a first subscriber identity module bank having anumber of positions for receiving a number of subscriber identitymodules; a first subscriber identity module server associated with thefirst subscriber identity module bank and responsive to requests toprovide subscriber identity information from the subscriber identitymodules, if any, received at the positions of the associated subscriberidentity module bank; and a subscriber identity module librarian havinga data structure that defines a set of relationships between a number ofsubscriber identity modules identifiers corresponding to respectivesubscriber identity modules, if any, and a network location of therespective subscriber identity module in a network.
 2. The system ofclaim 1, further comprising: at least a first subscriber identity modulecapable of providing a unique set of subscriber identity information,the first subscriber identity module received at one of the positions ofthe first subscriber identity module bank, the first subscriber identitymodule bank remotely located with respect to the wireless communicationsdevices.
 3. The system of claim 1, further comprising: at least a firstsubscriber identity module capable of providing a unique set ofsubscriber identity information and a non-unique set of subscribercustomization information, the first subscriber identity module receivedat one of the positions of the first subscriber identity module bank. 4.A system to remotely operate wireless communications devices, the systemcomprising: a first subscriber identity module bank having a number ofpositions for receiving a number of subscriber identity modules; a firstsubscriber identity module server associated with the first subscriberidentity module bank and responsive to requests to provide subscriberidentity information from the subscriber identity modules, if any,received at the positions of the associated subscriber identity modulebank; a subscriber identity module librarian having a data structurethat defines a set of relationships between a number of subscriberidentity modules identifiers corresponding to respective subscriberidentity modules, if any, and a network location of the respectivesubscriber identity module in a network; a second subscriber identitymodule bank having a number of positions for receiving a number ofsubscriber identity modules; at least a first subscriber identity modulecapable of providing a unique set of subscriber identity information,the first subscriber identity module received at one of the positions ofthe first subscriber identity module bank; at least a second subscriberidentity module capable of providing a unique set of subscriber identityinformation, the second subscriber identity module received at one ofthe positions of the second subscriber identity module bank; and asecond subscriber identity module server associated with the secondsubscriber identity module bank, wherein the data structure of thesubscriber identity module librarian stores a first relationship betweena first subscriber module identity and a network location of the firstsubscriber module including a network address of the first subscribermodule server, and wherein the data structure of the subscriber identitymodule librarian stores a second relationship between a secondsubscriber module identity and a network location of the secondsubscriber module including a network address of the second subscribermodule server.
 5. A system to remotely operate wireless communicationsdevices, the system comprising: a first subscriber identity module bankhaving a number of positions for receiving a number of subscriberidentity modules; a first subscriber identity module server associatedwith the first subscriber identity module bank and responsive torequests to provide subscriber identity information from the subscriberidentity modules, if any, received at the positions of the associatedsubscriber identity module bank; a subscriber identity module librarianhaving a data structure that defines a set of relationships between anumber of subscriber identity modules identifiers corresponding torespective subscriber identity modules, if any, and a network locationof the respective subscriber identity module in a network; a secondsubscriber identity module bank having a number of positions forreceiving a number of subscriber identity modules, the second subscriberidentity module bank associated with the first subscriber identitymodule server; at least a first subscriber identity module capable ofproviding a unique set of subscriber identity information, the firstsubscriber identity module received at one of the positions of the firstsubscriber identity module bank; at least a second subscriber identitymodule capable of providing a unique set of subscriber identityinformation, the second subscriber identity module received at one ofthe positions of the second subscriber identity module bank; and whereinthe data structure of the subscriber identity module librarian stores afirst relationship between a first subscriber module identity and anetwork location of the first subscriber module including a networkaddress of the first subscriber module server, and wherein the datastructure of the subscriber identity module librarian stores a secondrelationship between a second subscriber module identity and a networklocation of the second subscriber module including a network address ofthe first subscriber module server.
 6. The system of claim 1 wherein thefirst subscriber identity module server is responsive to requests tocreate an exclusive relationship between a wireless communicationsdevice and a one of the subscriber identity modules.
 7. A system toremotely operate wireless communications devices, the system comprising:a first subscriber identity module bank having a number of positions forreceiving a number of subscriber identity modules, the first subscriberidentity module bank located remotely from the wireless communicationsdevices; a first subscriber identity module server associated with thefirst subscriber identity module bank and responsive to provide thewireless communications devices with remote access to the subscriberidentity modules, if any, received at the positions of the associatedsubscriber identity module bank; and a subscriber identity modulelibrarian having a data structure that defines a set of relationshipsbetween a number of subscriber identity modules identifierscorresponding to respective subscriber identity modules, if any, and anetwork location of the respective subscriber identity module in anetwork.
 8. The system of claim 7 wherein the set of relationshipsbetween a number of subscriber identity module identifiers correspondingto respective subscriber identity modules, if any, and a networklocation comprises an address that uniquely identifies the position inthe first subscriber identity module bank in which a respective one ofthe first subscriber identity modules is received.
 9. The system ofclaim 7 wherein the set of relationships between a number of subscriberidentity module identifiers corresponding to respective subscriberidentity modules, if any, and a network location comprises a uniqueaddress that identifies the position in the first subscriber identitymodule bank in which a respective one of the first subscriber identitymodules is received and the subscriber identity module server with whichthe subscriber identity module bank is associated.
 10. The system ofclaim 7 wherein the first subscriber identity module bank has aplurality of positions.
 11. The system of claim 7 wherein the network isa remote testing network, separate from a wireless communicationsnetwork to be tested.
 12. The system of claim 7, the further systemcomprising: a remote test unit located in a cell of a cellular wirelesscommunications network and comprising at least two wirelesscommunications devices, operable to test the wireless communicationsnetwork via identities acquired from a first and a second one ofsubscriber identity modules located remotely from the two wirelesscommunications devices in the subscriber identity module bank.
 13. Asystem to operate wireless communications devices, the systemcomprising: a first subscriber identity module bank having a number ofpositions for receiving a number of subscriber identity modules; a firstsubscriber identity module server associated with the first subscriberidentity module bank and responsive to requests to provide subscriberidentity information from the subscriber identity modules, if any,received at the positions of the associated subscriber identity modulebank; and a subscriber identity module librarian having a data structurethat defines a set of relationships between a number of subscriberidentity module identifiers corresponding to respective subscriberidentity modules, if any, and a unique network location of therespective subscriber identity module in a network.